-
Notifications
You must be signed in to change notification settings - Fork 789
[class.access.base] No cv-qualification for access to inherited members #5068
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@jensmaurer @zygoloid @opensdh |
@languagelawyer: Even aside from the "member's class" issue, that generic restriction doesn't address the possibility of rejecting the access for access control or ambiguous inheritance reasons. Perhaps there is already yet another place that checks that, though. |
5f52813
to
0e1dc79
Compare
@jensmaurer I'm trying to use the "less clunky approach" now (with squashing and rebasing). |
... and discard cv for the left hand side operand.
@jensmaurer I've rebased the branch and slightly reworded the wording. |
Fixes #4952
The pointed-to naming class type should be identically cv-qualified.The class type of the left operand and the naming class of the member should be considered cv-unqualified for the purpose of accessibility.